FYI @nhojpatrick

In order to remove the direct commons-lang dependency from Jenkins core module, we need to:

• fix all plugins using commons-lang implied dependency ([JENKINS-72981] Remove Commons Lang 2 from core jenkinsci/jenkins#16404 spreadsheet)
• revert this and make it a detached plugin in Core

I started the removal in jenkinsci/jenkins#26105 but it won't be that easy without breaking a few plugins. cc @jtnord

make it a detached plugin in Core

That will not actually accomplish much then, because almost everyone will have it installed for all time.

That will not actually accomplish much then, because almost everyone will have it installed for all time.

It allows incremental delivery of the removal from core. (a detached plugin does not need to be bundled IIRC, and it could then be up to the user to manually install it if they have an issue with a plugin that has not migrated).

If you are worried about it existing for all time, then once all known plugins have been migrated the plugin could self destruct (ie uninstall itself, show an admin monitor etc etc)

Correct if I'm wrong but when you detach functionality from core into a plugin you specify the core version when that happened. And if any plugin is installed that depends on a core version older than that version the detached plugin gets installed. So basically at the beginning everyone gets the plugin installed because every plugin is older.
If you just remove it without declaring it a detached plugin, then this will lead to a bad experience for users because only at runtime you suddenly get ClassNotFound errors, if you're lucky you get them early at startup but worst case only after days. Reality is that many users don't read the release notes before upgrading and only check them if something goes wrong.